Skip to content

chore(deps): update dependency @stylistic/eslint-plugin to v4.4.1 #3047

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 6, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 6, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@stylistic/eslint-plugin (source) 4.4.0 -> 4.4.1 age adoption passing confidence

Release Notes

eslint-stylistic/eslint-stylistic (@​stylistic/eslint-plugin)

v4.4.1

Compare Source

Bug Fixes
  • keyword-spacing: check spaces around the type keyword in export declarations (#​797) (6854a3c)
Chores

v4.4.0

Compare Source

Features

v4.3.0

Compare Source

Features
Bug Fixes
  • eslint-plugin: only export interfaces in index (#​763) (93a4eb1)
  • handle new AST change on TSImportType (8f31461)
  • indent: handle ChainExpression and AwaitExpression when offsetTernaryExpressionsOffsetCallExpressions (#​751) (a1af663)
  • indent: wrong PropertyDefinition value offset when ts type have multiple line (#​774) (140e18f)
  • no-extra-parens: do not break specific ReturnStatement (#​738) (a375a92)
Documentation
Chores

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Jun 6, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @types/chai-subset@1.3.6
npm error Found: @types/chai@5.2.2
npm error node_modules/@types/chai
npm error   dev @types/chai@"5.2.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @types/chai@"<5.2.0" from @types/chai-subset@1.3.6
npm error node_modules/@types/chai-subset
npm error   dev @types/chai-subset@"1.3.6" from the root project
npm error
npm error Conflicting peer dependency: @types/chai@5.0.1
npm error node_modules/@types/chai
npm error   peer @types/chai@"<5.2.0" from @types/chai-subset@1.3.6
npm error   node_modules/@types/chai-subset
npm error     dev @types/chai-subset@"1.3.6" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-06-06T16_12_30_065Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-06-06T16_12_30_065Z-debug-0.log

@renovate renovate bot enabled auto-merge (squash) June 6, 2025 16:12
@renovate renovate bot merged commit 3e2c7d8 into main Jun 6, 2025
0 of 14 checks passed
@renovate renovate bot deleted the renovate/eslint-stylistic-monorepo branch June 6, 2025 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

0 participants